FYI:
It maybe helpfull to do a tar -tvf /src/mariux/beeroot/packages/zfs-0.7.3-0.x86_64.bee.tar.bz2, just to get an impression what is about to be installed.

I guess excluding will work also, but the rm in conjunction with -v gives one the chance to se what is going byebye, what in turn might be helpfull to judge the impact on the installation. Anyway there was a mail around concerning this topic -- too late ;)

start_cmd rm -vrf ${D}/usr/share/zfs/zfs-tests

und den developer muell /usr/include/lib{zfs,spl} gleich mit.

Braucht keine Sau.

I’d also like one commit per each program.

further purging:

• as for the tests, ok, but one would need an own installation to perform tests (what makes sense)
• but then the includes are needed to build the tests easily (i guess), also we never remove /usr/include, so I'd like to keep em.

commit structure:

• from my point of view spl/zfs belong together, so having just one commit is al right.

The spl package contains a splat tool only.

This utility uses the splat.ko kernel module to test the spl.ko kernel module. Run "modprobe splat" before invoking splat.

Are we going to have a splat module?

buczek@theinternet:~/git/bee-files (add-spl-zfs-0.7.3)$ sudo modprobe splat
modprobe: ERROR: could not insert 'splat': Unknown symbol in module, or unknown parameter (see dmesg)
buczek@theinternet:~/git/bee-files (add-spl-zfs-0.7.3)$ sudo splat
Unable to open /dev/splatctl: 2
Is the splat module loaded?

After I had pity with you pull request and merged it, I'd expected that you installed the packages....

Ashes on my head, I'm still focused on the raid topic, so this subproject went a bit under the floor.
OTOH I guess we need to switch to version 0.7.5, caus we've already established v. 0.7.5 modules in our new kernels, making this branch obsolete - sigh.

If you prepare a 0.7.5 pull request and it is merged and 0.7.5 gets installed, everything would be in sync again. So go ahead.

i know... it's on the todo list :)